Fix: Ambiguity Guard bypassed by common auxiliary verbs (is/are/was/were)#1520
Fix: Ambiguity Guard bypassed by common auxiliary verbs (is/are/was/were)#1520ivegotahunnitonit wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe memory parser no longer considers standalone auxiliary verbs strong factual evidence. A regression test verifies that input containing “is” and a misspelled decision term is classified as a decision. ChangesMemory parsing classification
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Signed-off-by: washim0988-art <islowashin@gmail.com>
|
Thanks for your contributions! We're closing this PR as these fixes have already been covered by another PR. |
This PR resolves the issue where the
MemoryParsingServiceambiguity guard is bypassed for most English sentences due to standalone auxiliary verbs (is,are,was,were) being present inSTRONG_FACT_PATTERNS.Standalone auxiliary verbs are too common and weak to bypass the ambiguity check. More specific structures are already mapped to correct confidence scores under classification rules.
Closes #1375
Part of Bug Challenge #770
Summary by CodeRabbit